Add testing of Gradle 9 #766
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oracle-contributor-agreement
bot
added
the
OCA Verified
Which versions of JUnit did you test this with? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While investigating #760 , I added testing of Gradle 9 to our build. This caused a few cascading issues:
KotlinApplicationWithTestsFunctionalTestwith a class initialized at build time errorThis error only happens when testing with GraalVM 17, not with 23. The workaround I have found is to add:
to the list of classes initialized at build time, but I'm not completely sure this is the right thing to do. /cc @sbrannen @marcphilipp
In any case it seems that the original issue doesn't occur outside of the context of Spring.